fix: Timeout if SQS policy created without explicit version in notification module #321
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add explicit IAM policy version (
"2012-10-17"
) to SQS policy in notification module to avoid API timeout during apply when modifying the resource. Very simple change to add what is already a default for the resource.Solution discovered in documentation while attempting to troubleshoot the issue (big ol' warning under the resource overview): Resource: aws_sqs_queue
Error:
Motivation and Context
Without the version explicitly stated, modifications to the SQS policy cause timeout during apply.
Breaking Changes
No breaking changes experienced. Explicitly setting what is already default.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)^^^ (WAS NOT NECESSARY)
examples/*
projectspre-commit run -a
on my pull request